[litmus] Introduce ExS, EIS and EOS variants#1716
[litmus] Introduce ExS, EIS and EOS variants#1716diaolo01 wants to merge 1 commit intoherd:masterfrom
Conversation
|
Don't you need to update |
|
@murzinv Do you mean litmus should explicitly set those bits when the variants are used? I introduced a check whether the bits are already enabled, otherwise throw an error. |
Well, in current form litmus would just accept new variants, but they have no effect. IIUC, these variants corresponds to |
b4b00b6 to
f2dcbf1
Compare
|
I tested this on hardware using the following test I get the following result: I opted for if |
|
I just glaceed over herd side of things and it seems that it is done with assumption that
Obviously, herd and litmus need to be aligned. |
murzinv
left a comment
There was a problem hiding this comment.
Code wise everything LGTM. Thanks!
| if Cfg.variant Variant_litmus.ConstPacField then | ||
| O.fi "if (!check_const_pac_field_variant(%S)) return 0;" doc.Name.name; | ||
| if Cfg.is_kvm && Cfg.variant Variant_litmus.ExS then | ||
| O.fi "if (!check_exs(%S)) return 0;" doc.Name.name ; |
There was a problem hiding this comment.
perhaps you could also move the eis and eos handling here as well?
There was a problem hiding this comment.
I have followed the split between check for feature and use feature as it's done for PAC. MTE does the check for feature within the mte_init function, which is in the same location in the code as eis/eos handling.
There was a problem hiding this comment.
MTE does the check for feature within the
mte_initfunction, which is in the same location in the code as eis/eos handling.
Unrelated to the PR. Perhaps MTE would benefit from the similar check/use split...
c78e04c to
4ffd2a3
Compare
| if Cfg.variant Variant_litmus.ConstPacField then | ||
| O.fi "if (!check_const_pac_field_variant(%S)) return 0;" doc.Name.name; | ||
| if Cfg.is_kvm && Cfg.variant Variant_litmus.ExS then | ||
| O.fi "if (!check_exs(%S)) return 0;" doc.Name.name ; |
There was a problem hiding this comment.
MTE does the check for feature within the
mte_initfunction, which is in the same location in the code as eis/eos handling.
Unrelated to the PR. Perhaps MTE would benefit from the similar check/use split...
relokin
left a comment
There was a problem hiding this comment.
Some minor nits, otherwise this PR looks good to me.
This PR enables litmus to run tests with
-variant exs, eos, eis. This mirrors the ability thatherdhas to run tests incatalogue/tests/aarch64-faults/.